home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970929-19971216
/
000013_news@newsmaster….columbia.edu _Tue Sep 30 11:38:23 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA15276
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 30 Sep 1997 11:38:22 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA02890
for kermit.misc@watsun; Tue, 30 Sep 1997 11:38:22 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: OS/2 Kermit odd behaviour with nn in terminal emulation
Date: 30 Sep 1997 15:38:20 GMT
Organization: Columbia University
Lines: 35
Message-ID: <60r6dc$7vg$1@apakabar.cc.columbia.edu>
References: <60r432$scd$1@darla.visi.com>
Reply-To: kermit-support@newsmaster.cc.columbia.edu
NNTP-Posting-Host: watsun.cc.columbia.edu
Keywords: OS/2,Kermit,nn
Xref: news.columbia.edu comp.protocols.kermit.misc:7776
In article <60r432$scd$1@darla.visi.com>, J. Otto Tennant <jot@visi.com> wrote:
: I have updated OS/2 kermit to 1.14.
:
: The vt220/vt320 terminal emulation seems bulletproof. I have no
: problems using it with elm and vi.
:
: When I attempt to follow-up a post using nn, though, WAIT appears and
: that's the end of it for that terminal session. This does not happen
: using vanilla telnet (although the OS/2 telnet is excruciatingly awkward
: to use, in this scenario it at least works.) The only way out is to
: kill off the window.
Your host is probably sending a C1 character which is ignored by IBM Telnet
but which is interpretted by Kermit as the start of a STRING definition.
What does Kermit/2 say in the lower right corner of the status line?
What happens if you use Alt-R to reset the terminal?
To debug the cause you can use SET TERMINAL DEBUG ON (Alt-D toggles) or
capture the session using LOG SESSION and examining what data is being sent.
Very likely the post uses a character set such as CP1252 (Windows
Latin1) which uses C1 control characters for things such as
apostrophe. Try this:
SET TERMINAL REMOTE-CHARACTER-SET CP1252
the problem will most likely go away.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025 * (212) 854-1344
http://www.columbia.edu/kermit/k95.html * kermit-support@columbia.edu